Methods, Apparatus, and System for Venue-Cast

ABSTRACT

A communications method for broadcasting an event is provided. This includes generating a plurality of media streams at an event and providing a service to receive the media streams. From the service, an interface can be generated to select a subset of the media streams. Media streams can include audio, video, or other formats that are selected from alternative broadcasting channels provided at the event.

CLAIM OF PRIORITY UNDER 35 U.S.C. 119

The present application for patent claims priority to ProvisionalApplication No. 60/777,532 entitled “VENUECAST SERVICE” filed Feb. 27,2006, and assigned to the assignee hereof and hereby expresslyincorporated by reference herein.

BACKGROUND

I. Field

The following description relates generally to communications systems,and more particularly to broadcasting and selecting various mediachannels for wireless devices within the confines of a venue such as asports arena.

II. Background

Wireless communication systems are widely deployed to provide varioustypes of communication; for instance, voice and/or data may be providedvia such wireless communication systems. A typical wirelesscommunication system, or network, can provide multiple users access toone or more shared resources. For instance, a system may use a varietyof multiple access techniques such as Frequency Division Multiplexing(FDM), Time Division Multiplexing (TDM), Code Division Multiplexing(CDM), Orthogonal Frequency Division Multiplexing (OFDM), and others.

Common wireless communication systems generally utilize one or more basestations that provide a coverage area. A typical base station cantransmit multiple data streams for broadcast, multicast and/or uni-castservices, wherein a data stream may be a stream of data that can be ofindependent reception interest to a user device. A user device withinthe coverage area of such base station can be employed to receive one,more than one, or all the data streams carried by the composite stream.Likewise, a user device can transmit data to the base station or anotheruser device.

Wireless communication systems may also be implemented to broadcastinformation related to a specific event, such as a television broadcastof a sporting event, a political speech, or the like. Viewers of suchtelevised or otherwise broadcast events may receive a signal thatprovides a single view of the event at any given time. Occasionally, abroadcaster may provide a “split-screen” view that shows the event fromtwo angles, however, the viewer, watching the event remotely, is unableto select a desired viewing angle or camera shot. Even viewers attendingthe event are limited to the viewing angle from their relative positionto the event source, or to prescribed camera angles on closed-circuittelevision screens. Therefore, a need exists in the art for systems andmethods that overcome the aforementioned deficiencies and facilitateenhancing user experience in a wireless communication environment.

SUMMARY

The following presents a simplified summary in order to provide a basicunderstanding of some aspects of the claimed subject matter. Thissummary is not an extensive overview, and is not intended to identifykey/critical elements or to delineate the scope of the claimed subjectmatter. Its sole purpose is to present some concepts in a simplifiedform as a prelude to the more detailed description that is presentedlater.

Multiple media channels and data streams are broadcast within a venuesuch as a sporting or music event, where users operating mobile devicescan receive and select various desired views or other media options asavailable. In general, sports facilities such as race tracks e.g.,NASCAR, Formula I, Kentucky Derby provide many different camera anglesor other media streams operating concurrently that can be selected forviewing from a device at such events. Such media streams are alsoavailable for other events including football, basketball, baseball, andconcerts for example. The viewer at home typically receives a singleview that the broadcast network distributes, or perhaps a limited numberof views at most due to the large bandwidth employed for high definition(HD) or Standard Definition (SD) transmission to the viewer. For a fanat the event, this need not be the case since many or all of the cameraviews can be supplied directly to the device or a handset, and morespecifically a cell phone or other mobile device.

In one aspect, a venue-cast application is provided that employs mobilebroadcast formats, where a subset of media channels including video,audio, text, and so forth are offered to users attending a given venue.In one specific example, a wireless operator may use availablecommunications frequencies and/or other owned spectrum allocation to runthe service. In most cases, the viewer of a sporting event is provided asingle video version of the event, yet there are often multiple cameraviews available at the actual venue. These are generally not availableeven to a person that attends the event, where the jumbo-tron or similarscreen runs a single camera view at a time. The multiple channels andassociated broadcast formats allow users to select from available andalternative media channels broadcast at a given event to enhance theoverall media experience at such events.

To the accomplishment of the foregoing and related ends, certainillustrative aspects are described herein in connection with thefollowing description and the annexed drawings. These aspects areindicative, however, of but a few of the various ways in which theprinciples of the claimed subject matter may be employed and the claimedsubject matter is intended to include all such aspects and theirequivalents. Other advantages and novel features may become apparentfrom the following detailed description when considered in conjunctionwith the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a high level block diagram of a system that is provided toillustrate venue casting in a communications environment.

FIG. 2 is a diagram of an example network support options for a device.

FIG. 3 illustrates an example interface considerations for a venue castdevice.

FIG. 4 illustrates optional device enabling considerations for a venuecast environment.

FIG. 5 illustrates multimedia handset considerations for a venue castdevice.

FIG. 6 illustrates an example venue cast process.

FIGS. 7 and 8 illustrate example logical modules for processing sequencemessages and registrations.

FIG. 9 illustrates an example communications apparatus that employssequential data to form communications links.

FIG. 10 illustrates an example communications system.

FIG. 11 illustrates an example end node.

FIG. 12 illustrates an example access node.

FIG. 13 illustrates an example end node communicating with an exampleaccess node.

DETAILED DESCRIPTION

Systems and methods are provided to facilitate multimedia experiences atlive events. In an aspect, a communications method for broadcasting anevent is provided. This includes generating a plurality of media streamsat an event and providing a service to receive the media streams. Fromthe service, an interface can be generated to select a subset of themedia streams. Media streams can include audio, video, or other formatsthat are selected from alternative broadcasting channels provided at theevent. In this manner, wireless operators can supplement their liveexperiences with various data streams that may depict other views ordata not available from a given perspective at the event.

Furthermore, various aspects are described herein in connection with aterminal. A terminal can also be called a system, a user device, asubscriber unit, subscriber station, mobile station, mobile device,remote station, remote terminal, access terminal, user terminal, useragent, or user equipment. A user device can be a cellular telephone, acordless telephone, a Session Initiation Protocol (SIP) phone, awireless local loop (WLL) station, a PDA, a handheld device havingwireless connection capability, a module within a terminal, a card thatcan be attached to or integrated within a host device (e.g., a PCMCIAcard) or other processing device connected to a wireless modem.

Moreover, aspects of the claimed subject matter may be implemented as amethod, apparatus, or article of manufacture using standard programmingand/or engineering techniques to produce software, firmware, hardware,or any combination thereof to control a computer or computing componentsto implement various aspects of the claimed subject matter. The term“article of manufacture” as used herein is intended to encompass acomputer program accessible from any computer-readable device, carrier,or media. For example, computer readable media can include but are notlimited to magnetic storage devices (e.g., hard disk, floppy disk,magnetic strips . . . ), optical disks (e.g., compact disk (CD), digitalversatile disk (DVD) . . . ), smart cards, and flash memory devices(e.g., card, stick, key drive . . . ). Additionally it should beappreciated that a carrier wave can be employed to carrycomputer-readable electronic data such as those used in transmitting andreceiving voice mail or in accessing a network such as a cellularnetwork. Of course, those skilled in the art will recognize manymodifications may be made to this configuration without departing fromthe scope or spirit of what is described herein.

Referring now to FIG. 1, a system 100 illustrates venue casting in awireless communications environment. A venue 110 provides an area orlocation where various types of media such as audio, video, text orother form can be generated with respect to an event or with respect toother events. As shown, a venue cast network 120 allows one or moreoperator or user terminals 130 to receive a plurality of media streams140 at the venue 110. For example, at a football contest which is playedat the venue 110, there may be six different camera views availablewhich can be associated with the media streams 140. At the same event,various audio streams may also be associated with the media streams 140.For instance, home team audio broadcasts and away team audio broadcasts.In yet another example, the media streams 140 may include another formof media such as textual information. For example, the media stream 140may include out of town scores or other information.

From the available media streams 140, operators of the terminals 130 canselect a subset of the streams from which to receive. For example, afirst terminal operator at 130 may decide to select camera views one andtwo as a split screen view on a wireless handset (e.g., cell phone, PDA,laptop PC) and select an out of town audio broadcast from a set ofpossible audio feeds. As will be described in more detail below,interfaces can be provided on the terminals 130 to allow users to selectdesired media stream for viewing or listening. In another aspect,notifications can be enabled to allow other sensory reception via themedia streams 140. For example, vibrate a phone when out of venue teamsscore changes as reflected by at least one of the media streams. Othernotifications can include substantially any type of output includingmechanical, beeps, pop-up displays, and so forth. As shown, optionalenabling components 150 can be provided. These components 150 can beprovided to limit participation with the venue cast network 120. Forexample, the terminals 130 may be required to receive an electronic keyor other enabling component 150 within the venue 110 before reception ofthe venue cast network 120 can commence. As will be described in moredetail below, location detection components may be employed as theoptional enabling component for respective venue cast services.

In one specific example, an attendee at an event can have an enhancedexperience by a wireless service provider operating a signal on adedicated frequency inside the venue 110. These services can be offeredin conjunction with an existing network, if desired. The venue castcontent over the network 120 and supplied by the media streams 140 maybe treated as a separate network, or as an integral part of the serviceoffering of an existing network. The separate network method providesthe most independence between the large area network and the venue castnetwork 120, however at the cost of operating at least two mediadistribution systems (MDS) i.e., one for each network. A second aspectintegrates the venue cast content over the network 120 into a singleshared network. This may be more robust as the presence of venue castlocations is easily discovered by the device or terminals 130 from alocal operator infrastructure (LOI) waveform, which announces thelocations as available RF signals per BCS and content Retailer. Theterminal 130 can infrequently check for presence of a venue castcarrier, while in a LOI with venue cast network 120 signals present.There can be issues associated with individuals obtaining access to thevenue cast network 120 from outside the venue. If contractuallyobligated to do so, the operator or user of the terminal 130 may have tophysically request keys (or other enabler 150) required for the event ata kiosk or similar booth inside the venue as will be described in moredetail below. Bluetooth or other similar short range communications canbe employed for receiving enabling codes and so forth. The requirementfor limiting access to the network 120 may be that only individualsphysically within the sports facility in question are allowed tosubscribe. Specific methods involving terminal positioning may beapplied as will be described in more detail below.

The terminals 130, which can be, for instance, a module such as an SDcard, a network card, a wireless network card, a computer (includinglaptops, desktops, personal digital assistants PDAs), mobile phones,smart phones, or any other suitable terminal that can be utilized toaccess the network 120. Generally, the terminals 130 access the network120 by way of an access node or nodes (not shown) within the venue. Forinstance, the terminals 130 can be communicatively coupled to an accessnode by way of a wired connection, such as an Ethernet cable, a USBconnection, etc. In another example, a connection between the terminals130 and access node may be wireless in nature, in which the access nodemay be a base station and the terminals may be a wireless. For instance,terminals 130 and access node may communicate by way of any suitablewireless protocol, including but not limited to Time Divisional MultipleAccess (TDMA), Code Division Multiple Access (CDMA), Frequency DivisionMultiple Access (FDMA), Orthogonal Frequency Division Multiplexing(OFDM), FLASH OFDM, Orthogonal Frequency Division Multiple Access(OFDMA), or any other suitable protocol.

Similarly to the terminals 130, the access node can be an access nodeassociated with a wired network or a wireless network. To that end, theaccess node can be, for instance, a router, a switch, or the like. Theaccess node can include one or more interfaces, e.g., communicationmodules, for communicating with other network nodes. Additionally,access node may be a base station (or wireless access point in the venue110) in a cellular type network, wherein base stations (or wirelessaccess points) are utilized to provide wireless coverage areas to aplurality of subscribers. Such base stations (or wireless access points)can be arranged to provide contiguous areas of coverage to one or morecellular phones and/or other wireless terminals 130 within the venue110.

Referring now to FIG. 2, example network support options for a device ina venue cast environment are illustrated. In this aspect, monitoringmodes for how devices can receive venue cast signals are described.Proceeding to 210, device support for venue cast via two networkinstances (or more) with a merged guide offering can be provided. Thiscan include where a device (or terminal) monitors at 220 for at least asecond network in specified LOI(s) of a large area network, for example.The type of monitoring provided at 220 may be considered as more powerefficient on the device for receiving venue cast signals. At 230, thedevice can monitor for venue cast signals at substantially all availabletimes. This option at 230 facilitates lower network side complexity.

Proceeding to 240, support options for venue cast broadcasting within anexisting network are considered. This can include allowing presence ofvenue cast to be visible within radio frequency (RF) allocation tablesof the network at 250, for example. Another support aspect of venue cast240 within existing networks includes having devices monitor forpresence of venue cast signals at 260 in LOI(s) that support venue castbroadcasting. At 270, a program guide that can be offered as part of aterminal interface allows multiple instances of venue cast within asingle LOI. Thus, in an aspect, different event sites can appear asdifferent channels where an exact listing may be distributed at thevenue and is distributed in band. Generally, for device side behavior,no additional network components are required. Therefore, devices thatdo not support the venue cast frequency band(s) do not display therespective venue cast channels. In another aspect, positioning systemscan be employed to locate whether or not a device is in range of one ormore available venue cast networks.

Referring to FIG. 3, example interface considerations 300 for a venuecast device are illustrated. In this aspect, some of the options forselecting and viewing available venue cast media streams are described.At 310, multiple camera views are considered for venue castapplications. As noted previously, other media than video can also beprovided. Generally, guide views or interfaces can be provided for thevenue cast suite of media signals. This includes building a scroll listfor multi-camera views at 310 e.g., 4:1 or N:1, and so forth.Multi-camera views may be built into the handset that decodes multiplemedia streams concurrently. Alternatively, this can also includedecoding of select packets or layers of multiple streams if multi-viewvideo coding is employed.

Multi-camera views at 310 may be sent as a separately encoded stream oras a single 3DAV or multi-view coded stream, for example that involvesprediction among views in addition to spatial and temporal prediction. Amulti-view quarter, quarter video graphics array (QQVGA) panel may beused as a base layer of a spatially layered codec at QVGA for example.Alternatively, the views at 310 may be coded at QQVGA resolution and onselection of a given view, providing enhanced up-sampling to QVGA torestore quality for a single view. Yet another aspect is if the base toenhancement layer bandwidth ratio is adapted to 1:3 or 1:4 for example.In this case, the base layer may carry the primary view and enhancementlayer may carry one to many secondary views. Base and enhancement layersmay be decoded to receive substantially all views and base layer onlymay be decoded for the primary view.

Proceeding to 320, custom views can be provided and received across avenue cast network. For example, custom views may include possiblyslower frame or update rate view—potentially enhanced through frameinterpolation or FRUC and pre-coded multi-view at full frame rate. Ascan be appreciated, screen or views can be mixed. Thus, one portion of ascreen on a terminal may display a regular frame rate view and anotherportion of a terminal screen may display a custom view 320. Proceedingto 330, the interface views 300 may include an integrated “pop to”cursor mode. This includes a highlighted view that may be in acquisitionfor the next second (or other time), and allows quick pop to full viewmode of the desired or selected media stream. Multi-views can remain inacquisition for quick pop back to multi-view of all media streams fromfull view of a selected subset of media streams.

At 340, codec considerations for terminals can include low latencyencoding that may be employed (e.g., maximum of a couple seconds) due tosports application or other real time event considerations. In anothercase, I data for the associated video codec may be carried in a separatemedia logic channel (MLC) to reduce power consumption for holdingmultiple channels in acquisition at the same time. Thus, for anequivalent to 1 second frame rate, switch frames may be substituted fora respective I frame, for example. A similar method may also be employedfor physical layers, such as DVB-H via specific configuration, such asall I frames in a common burst pattern which may be less efficient thanforward link only broadcasts.

Turning now to FIG. 4, optional device enabling considerations 400 for avenue cast environment are provided. In this aspect, limitations forwhich devices may be able to receive venue cast signals are described.As noted above, potential enabling components such as electronic keysmay be employed to limit reception of venue cast signals to paidparticipants of an event or otherwise valid subscribers to the event. At410, an optional means to assure the device is inside the venue, beyondlimited coverage of venue cast transmitter can include a Kiosk at theevent that provides unit encrypted keys for the event inside thefacility. The Kiosk 410 may use paper or may use Bluetooth or othershort range verification frequency. In one example, the bar code on aticket may be scanned (by device or kiosk) and employed as part of asubscription enabler to the service.

At 420, enabling of a device may include employing positioning of thedevice to determine its location. This may employ multiple transmitterswithin the venue or concurrent support of large area and venue cast. At430, a device may employ a global positioning satellite (GPS)positioning to determine location and thus confirm that it is enabledfor the respective event. With GPS positioning for determining devicelocations, outdoor locations may be best suited for GPS locationtechnologies. As can be appreciated, substantially any technology thatenables devices within the venue to receive venue cast signals and toexclude devices outside the venue can be employed.

Referring, to FIG. 5, multimedia handset considerations for a venue castdevice 500 are illustrated. In this aspect, nuances with support forvenue cast signals at the device 500 are considered. Proceeding to 510,device infrastructure support is considered. In multimode (multiplemultimedia physical layers) the handset 500, venue cast and large areanetworks do not have to share the same physical layer. Thus, handsets500 may be used for venue cast within a digital video broadcasting(DVB-H) infrastructure or a digital media broadcasting (T-DMB)infrastructure, for example. As can be appreciated, additionalinfrastructure permutations are possible. At 520, waveform positioningfor devices are provided. In this aspect, positioning can be built intothe respective waveforms that support venue cast. This can include afast acquisition via layer synchronization signals and provide featuressuch as an all I and switch frame media logic channel (MLC). At 530,subscription options can be provided for the handset 500. As notedpreviously, venue casting maybe offered as a subscription on any methodthat is supported e.g., per event IPPV, or seasonally. Due to the natureof broadcasting contractual obligations, per event key delivery may berequired to limit participation of venue cast to ticketed or subscribingcustomers. In general, the handset 500 can be employed as part of asystem that provides features to execute a multi-view, simulcast systemat a venue and integrate such views with an existing mobile multimediato handset network offering. Hybrid applications are also possible wheresome components of the handset support venue cast applications and othercomponents of the handset support non-venue cast applications such asvoice and text messaging for example.

Referring to FIG. 6, a venue cast process 600 is illustrated. While, forpurposes of simplicity of explanation, the methodology is shown anddescribed as a series of acts, it is to be understood and appreciatedthat the methodology is not limited by the order of acts, as some actsmay, in accordance with one or more embodiments, occur in differentorders and/or concurrently with other acts from that shown and describedherein. For example, those skilled in the art will understand andappreciate that a methodology could alternatively be represented as aseries of interrelated states or events, such as in a state diagram.Moreover, not all illustrated acts may be utilized to implement amethodology in accordance with the claimed subject matter.

Proceeding to 602, the process starts, where various media streams arebroadcast according to one or more channels or layers at 604. As notedabove, such media streams can include video streams for multiple cameraangles, audio streams for alternative listening experiences, or otherdata streams such as textual streams for reviewing information inaccordance with or peripheral to the event. At 606, devices are enabledto receive multiple channels or data streams via a venue cast signal orsuite of signals. This can include optionally enabling devices at theevent to limit participation of venue cast signals to subscribingcustomers. As noted previously, kiosks can be provided to receiveenabling keys at the respective devices or other means can include usingavailable positioning technologies to determine that a device is withinthe boundaries defined for a given venue.

At 608, interfaces are provided for devices to select from availablemedia options provided at the venue. This can include pop to cursordisplays that show a set of available signals than can be selected,where device control buttons can be employed to select a subset forviewing or other media experience. For instance, from a set of fouravailable media views, device control buttons could select a subset ofviews for a split screen display of a single view for full screendisplay. Proceeding to 610, desired views or media streams are selectedfrom the interface provided at 608. At 610, after a media option isselected, media output is generated for a respective handset orterminal. At 620, the process 600 ends or repeats at 602 as other mediaoptions are determined and selected.

Turning now to FIGS. 7 and 8 collectively, systems are provided thatrelate to venue cast broadcasting with respect to a terminal, operatornetworks, access nodes, and traffic flows therewith. The systems arerepresented as a series of interrelated functional blocks, which canrepresent functions implemented by a processor, software, hardware,firmware, or any suitable combination thereof.

Referring specifically to FIG. 7, a system 700 that facilitatescommunications across a venue cast network. The system 700 includes alogical module 702 for broadcasting a plurality of media streams at anevent and a logical module 704 for enabling a service to receive themedia streams. A logical module 706 can be employed for interfacing tothe media streams in order to select a subset of the media streams fordesired viewing.

Now referring to FIG. 8, a system 800 that facilitates communicationsfrom a receiving device across a venue cast network. The system 800includes a logical module 802 for receiving a plurality of media streamsat an event and a logical module 804 for enabling a service to receivethe media streams. A logical module 806 can be utilized for interfacingto the media streams in order to select a subset of the media streamsfor desired viewing.

FIG. 9 illustrates a communications apparatus 900 that can be a wirelesscommunications apparatus, for instance, such as a wireless terminalAdditionally or alternatively, communications apparatus 900 can beresident within a wired network. Communications apparatus 900 caninclude memory 902 that can retain instructions for configuring suchapparatus with respect to venue cast data for a terminal (and trafficflows associated therewith). Additionally, communications apparatus 900may include a processor 904 that can have several modules or units toexecute instructions within memory 902 and/or instructions received fromanother network device, wherein the instructions can relate toconfiguring communications apparatus 900 or a related communicationsapparatus. For example, the processor can execute an interface whereavailable venue cast options can be selected. After a given selection,for instance if a single view is selected, the respective camera angleassociated with the selection can be displayed as a full screen optionon the respective apparatus 900.

To provide additional context for one or more embodiments describedherein, FIG. 10 is provided to illustrate an example communicationsystem 1000 that comprises a plurality of nodes interconnected bycommunications links. The system 1000 may use Orthogonal FrequencyDivision Multiplexing (OFDM) signals to communicate information overwireless links. However, other types of signals, e.g., Code DivisionMultiple Access (CDMA) signals or Time Division Multiple Access (TDMA)signals, are also contemplated (together with signals utilized inland-based networks). Nodes in the communication system 1000 exchangeinformation using signals, e.g., messages, based on communicationprotocols, e.g., the Internet Protocol (IP). The communications links ofthe system 1000 may be implemented, for example, using wires, fiberoptic cables, and/or wireless communications techniques. The system 1000includes a plurality of end nodes 1002-1012, which access thecommunication system 1000 by way of a plurality of access nodes1014-1018. End nodes 1002-1012 may be, e.g., wireless communicationdevices or terminals, and the access nodes 1014-1018 may be, e.g.,wireless access routers or base stations. Communication system 1000 alsoincludes a number of other nodes 1020-1030 that are used to provideinterconnectivity or to provide specific services or functions.

Communications system 1000 depicts a network 1060 that includes accesscontrol node 1020, mobility support node 1022, policy control node 1024,and application server node 1026, all of which are connected to anintermediate network node 1028 by a corresponding network link1032-1038, respectively. In some embodiments, the access control node,e.g., a Remote Authentication Dial In User Service (RADIUS) or Diameterserver, supports authentication, authorization, and/or accounting of endnodes and/or services associated with end nodes. In some embodiments,mobility support node 1022, e.g., a Mobile IP home agent and/or contexttransfer server, supports mobility, e.g., handoff, of end nodes betweenaccess nodes, e.g., by way of redirection of traffic to/from end nodesand/or transfer of state associated with end nodes between access nodes.In some embodiments, policy control node 1024, e.g., a policy server orPolicy Decision Point (PDP), supports policy authorization for servicesor application layer sessions. In some embodiments, application servernode 1026, e.g., a Session Initiation Protocol server, streaming mediaserver, or other application layer server, supports session signalingfor services available to end nodes and/or provides services or contentavailable to end nodes.

Intermediate network node 1028 in network 1060 providesinterconnectivity to network nodes that are external from theperspective of network 1060 by way of network link 1034. Network link1034 is connected to intermediate network node 1030, which providesfurther connectivity to access nodes 1014, 1016, and 1018 by way ofnetwork links 1036-1040, respectively. Each access node 1014-1018 isdepicted as providing connectivity to end nodes 1002-1012, respectively,by way of corresponding access links 1042-1052, respectively. Incommunication system 1000, each access node 1014-1018 is depicted asusing wireless technology, e.g., wireless access links, to provideaccess. Wired technology may also be utilized, however, in connectionwith provision of access. A radio coverage area, e.g., communicationscells 1054-1058 of each access node 1014-1018, is illustrated as acircle surrounding the corresponding access node.

Communication system 1000 can be used as a basis for the description ofvarious embodiments described herein. Alternative embodiments includevarious network topologies, where a number and type of nodes (includingnetwork nodes, access nodes, end nodes, as well as various control,support, and server nodes), a number and type of links, andinterconnectivity between various nodes may differ from that ofcommunication system 1000. Additionally, some of the functional entitiesdepicted in communication system 1000 may be omitted or combined.Location or placement of these functional entities may also be varied.

FIG. 11 provides an illustration of an example end node 1100, e.g.,wireless terminal. End node 1100 is a representation of an apparatusthat may be used as any one of end nodes 1002-1012 (FIG. 10). End node1100 includes a processor 1102, a wireless communication interfacemodule 1104, a user input/output interface 1106 and memory 1108 coupledtogether by a bus 1110. Accordingly, by way of bus 1110, the variouscomponents of the end node 1100 can exchange information, signals anddata. Components 1102-1108 of end node 1100 can be located inside ahousing 1112.

Wireless communication interface module 1104 provides a mechanism bywhich the internal components of end node 1100 can send and receivesignals to/from external devices and network nodes, e.g., access nodes.Wireless communication interface module 1104 includes, e.g., a receivermodule 1114 with a corresponding receiving antenna 1116 and atransmitter module 1118 with a corresponding transmitting antenna 1120used for coupling end node 1100 to other network nodes, e.g., by way ofwireless communications channels.

End node 1100 also includes a user input device 1122, e.g., keypad, anda user output device 1124, e.g., display, which are coupled to bus 1110through user input/output interface 1106. Thus, user input/outputdevices 1122 and 1124 can exchange information, signals and data withother components of end node 1100 by way of user input/output interface1106 and bus 1110. User input/output interface 1106 and associateddevices 1122 and 1124 provide mechanisms by which a user can operate endnode 1100 to accomplish various tasks. In particular, user input device1122 and user output device 1124 provide functionality that allows auser to control end node 1100 and applications, e.g., modules, programs,routines and/or functions, that execute in memory 1108 of end node 1100.

Processor 1102, under control of various modules, e.g., routines,included in memory 1108 controls operation of end node 1100 to performvarious signaling and processing. The modules included in memory 1108are executed on startup or as called by other modules. Modules mayexchange data, information, and signals when executed. Modules may alsoshare data and information when executed. Memory 1108 of end node 1100includes a control signaling module 1126, an application module 1128,and a traffic control module 1130, which further includes configurationinformation 1132 and various additional modules.

Control signaling module 1126 controls processing relating to receivingand sending signals, e.g., messages, for controlling operation and/orconfiguration of various aspects of end node 1100 including, e.g.,traffic control module 1130 as well as configuration information 1132and various additional modules included. In some embodiments, controlsignaling module 1126 can include state information, e.g., parameters,status and/or other information, relating to operation of end node 1100and/or one or more signaling protocols supported by control signalingmodule 1126. In particular, control signaling module 1126 may includeconfiguration information, e.g., end node identification informationand/or parameter settings, and operational information, e.g.,information about current processing state, status of pending messagetransactions, etc.

Application module 1128 controls processing and communications relatingto one or more applications supported by end node 1100. In someembodiments, application module 1128 processing can include tasksrelating to input/output of information by way of the user input/outputinterface 1106, manipulation of information associated with anapplication, and/or receiving or sending signals, e.g., messages,associated with an application. In some embodiments, application module1128 includes state information, e.g., parameters, status and/or otherinformation, relating to operation of one or more applications supportedby application module 1128. In particular, application module 1128 mayinclude configuration information, e.g., user identification informationand/or parameter settings, and operational information, e.g.,information about current processing state, status of pending responses,etc. Applications supported by application module 1128 include, e.g.,Voice over IP (VoIP), web browsing, streaming audio/video, instantmessaging, file sharing, gaming, etc.

Traffic control module 1130 controls processing relating to receivingand sending data information, e.g., messages, packets, and/or frames,through wireless communication interface module 1104. The exampletraffic control module 1130 includes configuration information 1132 aswell as various additional modules that control various aspects of QoSfor packets and/or traffic flows, e.g., associated sequences of packets.Various additional modules are included, in some embodiments, to performparticular functions and operations as needed to support specificaspects of traffic control. Modules may be omitted and/or combined asneeded depending on the functional requirements of traffic control. Adescription of each additional module included in traffic control module1130 follows.

An admission control module 1134 maintains information relating toresource utilization/availability and determines if sufficient resourcesare available to support QoS parameters desirably associated withparticular traffic flows. Resource availability information maintainedby admission control module 1134 includes, e.g., packet and/or framequeuing capacity, scheduling capacity, as well as processing and memorycapacity needed to support one or more traffic flows. Control signalingmodule 1126, application module 1128, and/or other modules included inend node 1100 may query admission control module 1134 to determine ifsufficient resources are available to support a new or modified trafficflow, where the admission control determination is a function of QoSparameters of the particular traffic flow and QoS parameters definedwithin a profile. Configuration information 1132 can includeconfiguration information, e.g., parameters settings, that affect theoperation of admission control module 1134, e.g., an admission controlthreshold value that indicates percentage of resource that may beallocated prior to rejecting additional requests.

An uplink scheduler module 1136 controls processing relating totransmission scheduling, e.g., order and/or timing, and allocation oftransmission resources, e.g., information coding rate, transmission timeslots, and/or transmission power, for data information, e.g., messages,packets, and/or frames, to be sent by way of wireless communicationinterface module 1104, e.g., from end node 1100 to an access node.Uplink scheduler module 1136 can schedule transmissions and allocatetransmission resources as a function of QoS parameters associated withone or more traffic flows. In some embodiments, scheduling and/orresource allocation operations performed by uplink scheduler module 1136are additionally a function of channel conditions and other factors,e.g., power budget.

An uplink PHY/MAC module 1138 controls physical (PHY) layer and MediaAccess Control (MAC) layer processing relating to sending datainformation, e.g., messages, packets, and/or frames, by way of wirelesscommunication interface module 1104, e.g., from end node 1100 to anaccess node. For instance, operation of uplink PHY/MAC module 1138includes both sending and receiving control information, e.g., signalsor messages, to coordinate sending of data information, e.g., messages,packets, and/or frames. Configuration information 1132 can includeconfiguration information, e.g., parameters settings, that affect theoperation of uplink PHY/MAC module 1138, e.g., a frequency, band,channel, spreading code or hoping code to be used for transmissions, anidentifier associated with end node 1100, a request dictionaryprescribing use of an assignment request channel, etc.

An uplink LLC (ARQ) module 1140 controls Logical Link Control (LLC)layer processing relating to sending data information, e.g., messages,packets, and/or frames, through wireless communication interface module1104, e.g., from end node 1100 to an access node. Uplink LLC (ARQ)module 1140 includes processing associated with Automatic Repeat Request(ARQ) capabilities, e.g., retransmission of lost packets or frames.Uplink LLC (ARQ) module 1140 can, for instance, further includeprocessing relating to addition of an LLC header and/or trailer tohigher layer messages, e.g., packets, to provide additionalfunctionality, e.g., multi-protocol multiplexing/demultiplexing by wayof a type field or error detection through utilization of a checksumfield. Uplink LLC (ARQ) module 1140 can additionally performfragmentation of higher layer messages, e.g., packets, into multiplesub-portions, e.g., frames to be sent by uplink PHY/MAC module 1140.Configuration information 1132 can include configuration informationthat affect operation of uplink LLC (ARQ) module 1140, e.g., an ARQwindow size, maximum number of retransmissions, a discard timer, etc.

An uplink queue management module 1142 maintains information andcontrols processing relating to storage of data information to be sentby way of wireless communication interface module 1104, e.g., from endnode 1100 to an access node. Uplink queue management module 1142 can,for example, control storage of data information awaiting transmissionand maintain state information regarding data information awaitingtransmission on a per traffic flow basis, e.g., packets associated witheach traffic flow may be stored in separate queues. For instance, uplinkqueue management module 1142 supports a variety of queue managementtechniques and/or capabilities, e.g., head drop, tail drop, as well asvarious Active Queue Management (AQM) mechanisms such as Random EarlyDetection (RED). Configuration information 1132 can includeconfiguration information that affects operation of uplink queuemanagement module 1142, such as a queue limit, drop strategy, and/or AQMthresholds associated with one or more traffic flows.

An uplink classifier module 1144 controls processing relating toidentification of data information as belonging to particular trafficflows prior to being sent by way of the wireless communication interfacemodule 1104, e.g., from end node 1100 to an access node. In someembodiments, messages, packets, and/or frames to be sent throughutilization of wireless communication interface module 1104 areclassified as belonging to one of a variety of traffic flows by uplinkclassifier module 1144 based on inspection of one or more header and/orpayload fields. Results of classification by uplink classifier module1144 can affect the treatment of classified data information by uplinkqueue management module 1142 as well as other modules within memory1108. For example, the results may determine a particular queue themessage, packet, and/or frame will be associated with for storage andfurther affect subsequent processing such as scheduling. Configurationinformation can include configuration information that affect operationof uplink classifier module 1144, e.g., a set of one or more classifierfilter rules that prescribe criteria used to associate data information,e.g., messages, packets, and/or frames, as belonging to one or moretraffic flows.

A downlink PHY/MAC module 1146 controls PHY layer and MAC layerprocessing relating to receiving data information by way of wirelesscommunication interface module 1104. Operation of downlink PHY/MACmodule 1146 can include both sending and receiving control informationto coordinate receiving of data information. Configuration information1104 can include configuration information that affect operation ofdownlink PHY/MAC module 1146, e.g., a frequency, band, channel,spreading code or hoping code to be used for reception, an identifierassociated with end node 1100, etc.

A downlink LLC (ARQ) module 1148 controls LLC layer processing relatingto receiving data information by way of wireless communication interfacemodule 1104. Downlink LLC (ARQ) module 1148 includes processingassociated with ARQ capabilities, e.g., retransmission of lost packetsor frames. For example, downlink LLC (ARQ) module 1148 can furtherinclude processing relating to an LLC header and/or trailer thatencapsulates higher layer messages, which provides additionalfunctionality, e.g., multi-protocol multiplexing/demultiplexing througha type field or error detection by way of a checksum field. Downlink LLC(ARQ) module 1148 can also perform reassembly of frames received by thedownlink PHY/MAC module 1146 into higher layer messages. Configurationinformation 1132 can, and in some embodiments does, includeconfiguration information, e.g., parameters settings, that affectoperation of downlink LLC (ARQ) module 1148, e.g., an ARQ window size,maximum number of retransmissions, a discard timer, etc.

FIG. 12 provides a detailed illustration of an example access node 1200implemented in accordance with the present invention. The access node1200 is a detailed representation of an apparatus that may be used asany one of the access nodes 1014-1018 depicted in FIG. 10. In the FIG.12 embodiment, access node 1200 includes a processor 1202, memory 1204,a network/internetwork interface module 1206 and a wirelesscommunication interface module 1208, coupled together by bus 1210.Accordingly, by way of bus 1210 the various components of access node1200 can exchange information, signals and data. The components1202-1210 of access node 1200 are located inside a housing 1212.

Network/internetwork interface module 1206 provides a mechanism by whichthe internal components of access node 1200 can send and receive signalsto/from external devices and network nodes. Network/internetworkinterface module 1206 includes a receiver module 1214 and a transmittermodule 1216 used for coupling node 1200 to other network nodes, e.g.,through copper wires or fiber optic lines. Wireless communicationinterface module 1208 also provides a mechanism by which the internalcomponents of access node 1200 can send and receive signals to/fromexternal devices and network nodes, e.g., end nodes. Wirelesscommunication interface module 1208 includes, e.g., a receiver module1218 with a corresponding receiving antenna 1220 and a transmittermodule 1222 with a corresponding transmitting antenna 1224. Wirelesscommunication interface module 1208 is used for coupling access node1200 to other nodes, e.g., by way of wireless communication channels.

Processor 1202 under control of various modules, e.g., routines,included in memory 1204 controls operation of access node 1200 toperform various signaling and processing. The modules included in memory1204 are executed on startup or as called by other modules. Modules mayexchange data, information, and signals when executed. Modules may alsoshare data and information when executed. In the FIG. 12 embodiment,memory 1204 of access node 1200 includes a control signaling module 1226and a traffic control module 1228, which further includes configurationinformation 1230 and various additional modules 1232-1254.

Control signaling module 1226 controls processing relating to receivingand sending signals, e.g., messages, for controlling operation and/orconfiguration of various aspects of access node 1200 including, e.g.,traffic control module 1228 as well as configuration information 1230and the various additional modules included therein 1232-1254. Forinstance, control signaling module 1226 includes state information,e.g., parameters, status and/or other information, relating to operationof access node 1200 and/or one or more signaling protocols supported bycontrol signaling module 1226. In particular, control signaling module1226 may include configuration information, e.g., access nodeidentification information and/or parameter settings, and operationalinformation, e.g., information about current processing state, status ofpending message transactions, etc.

Traffic control module 1228 controls processing relating to receivingand sending data information, e.g., messages, packets, and/or frames, byway of wireless communication interface module 1208. For instance,traffic control module can include configuration information 1230 aswell as various additional modules 1232-1254 that control variousaspects of quality of service for packets and/or traffic flows, e.g.,associated sequences of packets. In some embodiments, traffic controlmodule 1228 includes state information, e.g., parameters, status and/orother information, relating to operation of access node 1200, trafficcontrol module 1228, and/or one or more of the various additionalmodules included therein 1232-1254. Configuration information 1230,e.g., parameter settings, determines, affects and/or prescribesoperation of traffic control module 1228 and/or the various additionalmodules included therein 1232-1254. The various additional modules areincluded, in some embodiments, to perform particular functions andoperations as needed to support specific aspects of traffic control. Invarious embodiments, modules may be omitted and/or combined as neededdepending on the functional requirements of traffic control. Adescription of each additional module included in traffic control module1228 follows.

Admission control module 1232 maintains information relating to resourceutilization/availability and determines if sufficient resources areavailable to support quality of service requirements of particulartraffic flows. Resource availability information maintained by admissioncontrol module 1232 includes, e.g., packet and/or frame queuingcapacity, scheduling capacity, as well as processing and memory capacityneeded to support one or more traffic flows. Control signaling module1226 and/or other modules included in access node 1200 can queryadmission control module 1232 to determine if sufficient resources areavailable to support a new or modified traffic flow, where the admissioncontrol determination is a function of the quality of servicerequirements of the particular traffic flow and/or the availableresources. Configuration information 1230 can include configurationinformation, e.g., parameters settings, that affect the operation ofadmission control module 1232, e.g., an admission control thresholdvalue that indicates the percentage of resource that may be allocatedprior to rejecting additional requests.

Uplink scheduler module 1234 controls processing relating totransmission scheduling, e.g., order and/or timing, and allocation oftransmission resources, e.g., information coding rate, transmission timeslots, and/or transmission power, for data information, e.g., messages,packets, and/or frames, to be sent from one or more end nodes to theaccess node by way of wireless interface module 1208. Uplink schedulermodule 1234 can schedule transmissions and allocate transmissionresources as a function of the quality of service requirements and/orconstraints associated with one or more traffic flows and/or one or moreend nodes. Configuration information 1230 can include configurationinformation that affect the operation of uplink scheduler module 1234,e.g., a priority, rate bound, latency bound, and/or sharing weightassociated with one or more traffic flows and/or end nodes. In someembodiments, scheduling and/or resource allocation operations performedby uplink scheduler module 1234 are additionally a function of channelconditions and other factors, e.g., power budget.

Downlink scheduler module 1236 controls processing relating totransmission scheduling, e.g., order and/or timing, and allocation oftransmission resources, e.g., information coding rate, transmission timeslots, and/or transmission power, for data information, e.g., messages,packets, and/or frames, to be sent from access node 1200 to one or moreend nodes through wireless interface module 1208. Downlink schedulermodule 1236 can schedule transmissions and allocate transmissionresources as a function of the quality of service requirements and/orconstraints associated with one or more traffic flows and/or one or moreend nodes. Configuration information 1230 can include configurationinformation that affects the operation of downlink scheduler module1236, e.g., a priority, rate bound, latency bound, and/or sharing weightassociated with one or more traffic flows and/or end nodes. In someembodiments, scheduling and/or resource allocation operations performedby the downlink scheduler module 1236 are additionally a function ofchannel conditions and other factors, e.g., power budget.

Uplink traffic conditioner module 1238 controls processing relating totraffic conditioning, e.g., metering, marking, policing, etc., for datainformation, e.g., messages, packets, and/or frames, received by way ofwireless interface module 1208, e.g., from an end node to access node1200. Uplink traffic conditioner module 1238 can condition traffic,e.g., meter, mark and/or police, as a function of the quality of servicerequirements and/or constraints associated with one or more trafficflows and/or one or more end nodes. Configuration information 1230 caninclude configuration information that affects the operation of uplinktraffic conditioner module 1238, e.g., a rate bound, and/or markingvalue associated with one or more traffic flows and/or end nodes.

Uplink classifier module 1240 controls processing relating toidentification of data information, e.g., messages, packets, and/orframes, received through wireless interface module 1208, e.g., from anend node to access node 1200, as belonging to particular traffic flowsprior to being processed by uplink traffic conditioner module 1238. Insome embodiments, messages, packets, and/or frames received throughwireless communication interface module 1208 are classified as belongingto one of a variety of traffic flows by uplink classifier module 1240based on inspection of one or more header and/or payload fields. Theresults of classification by uplink classifier module 1240 can affectthe treatment of the classified data information, e.g., messages,packets, and/or frames, by uplink traffic conditioner module 1238, e.g.,the results may determine a particular data structure or state machinethe message, packet, and/or frame will be associated with and furtheraffect subsequent processing such as metering, marking, and/or policing.Configuration information 1230 can include configuration informationthat affects the operation of uplink classifier module 1240, e.g., a setof one or more classifier filter rules that prescribe criteria used toassociate data information, e.g., messages, packets, and/or frames, asbelonging to one or more traffic flows.

Uplink LLC (ARQ) module 1242 controls LLC layer processing relating toreceiving data information, e.g., packets and/or frames, by way ofwireless communication interface module 1208, e.g., from an end node toaccess node 1200. Uplink LLC (ARQ) module 1242 includes processingassociated with ARQ capabilities, e.g., retransmission of lost packetsor frames. In some embodiments, uplink LLC (ARQ) module 1242 furtherincludes processing relating to an LLC header and/or trailer thatencapsulates higher layer messages, e.g., packets, which providesadditional functionality, e.g., multi-protocolmultiplexing/demultiplexing through a type field or error detection byway of a checksum field. Uplink LLC (ARQ) module 1242 can also performreassembly of frames received by uplink PHY/MAC module 1244 into higherlayer messages, e.g., packets. The configuration information 1230 caninclude configuration information that affects the operation of uplinkLLC (ARQ) module 1242, e.g., an ARQ window size, maximum number ofretransmissions, a discard timer, etc.

Uplink PHY/MAC module 1244 controls PHY layer and MAC layer processingrelating to receiving data information, e.g., packets and/or frames, byway of wireless communication interface module 1208, e.g., from an endnode to access node 1200. In some embodiments, operation of uplinkPHY/MAC module 1244 includes both sending and receiving controlinformation, e.g., signals or messages, to coordinate receiving of datainformation, e.g., messages, packets, or frames. Configurationinformation 1230 can include configuration information that affects theoperation of uplink PHY/MAC module 1244, e.g., a frequency, band,channel, spreading code or hopping code to be used for reception, anidentifier associated with access node 1200, etc.

Downlink classifier module 1246 controls processing relating toidentification of data information, e.g., messages, packets, and/orframes, as belonging to particular traffic flows prior to being sentthrough wireless communication interface module 1208, e.g., from accessnode 1200 to an end node. In some embodiments, messages, packets, and/orframes to be sent by way of wireless communication interface module 1208are classified as belonging to one of a variety of traffic flows bydownlink classifier module 1246 based on inspection of one or moreheader and/or payload fields. The results of classification by downlinkclassifier module 1246 can affect the treatment of the classified datainformation, e.g., messages, packets, and/or frames, by downlink queuemanagement module 1250 and other modules 1248, 1252, and 1254, e.g., theresults may determine a particular queue the message, packet, and/orframe will be associated with for storage and further affect subsequentprocessing such as scheduling. Configuration information 1230 caninclude configuration information, e.g., parameters settings, thataffect the operation of downlink classifier module 1246, e.g., a set ofone or more classifier filter rules that prescribe criteria used toassociate data information, e.g., messages, packets, and/or frames, asbelonging to one or more traffic flows.

Downlink traffic conditioner module 1248 controls processing relating totraffic conditioning, e.g., metering, marking, policing, etc., for datainformation, e.g., messages, packets, and/or frames, to be sent by wayof wireless interface module 1208, e.g., from access node 1200 to an endnode. Downlink traffic conditioner module 1248 can condition traffic,e.g., meter, mark and/or police, as a function of the quality of servicerequirements and/or constraints associated with one or more trafficflows and/or one or more end nodes. Configuration information 1230 caninclude configuration information that affects the operation of downlinktraffic conditioner module 1248, e.g., a rate bound, and/or markingvalue associated with one or more traffic flows and/or end nodes.

Downlink queue management module 1250 maintains information and controlsprocessing relating to storage of data information, e.g., messages,packets, and/or frames, to be sent by way of wireless communicationinterface module 1208, e.g., from access node 1200 to an end node.Downlink queue management module can control storage of data informationawaiting transmission and maintain state information regarding datainformation awaiting transmission on a per traffic flow basis, e.g.,packets associated with each traffic flow may be stored in separatequeues. In some embodiments of, Downlink queue management module 1250supports a variety of queue management techniques and/or capabilities,e.g., head drop, tail drop, as well as various AQM mechanisms such asRED. Configuration information 1230 can include configurationinformation that affects the operation of downlink queue managementmodule 1250, e.g., a queue limit, drop strategy, and/or AQM thresholdsassociated with one or more traffic flows.

Downlink LLC (ARQ) module 1252 controls LLC layer processing relating tosending data information, e.g., messages, packets, and/or frames, by wayof wireless communication interface module 1208, e.g., from access node1200 to an end node. Downlink LLC (ARQ) module 1252 includes processingassociated with ARQ capabilities, e.g., retransmission of lost packetsor frames. In some embodiments, downlink LLC (ARQ) module 1252 furtherincludes processing relating to the addition of an LLC header and/ortrailer to higher layer messages, e.g., packets, to provide additionalfunctionality, e.g., multi-protocol multiplexing/demultiplexing througha type field or error detection by way of a checksum field. Downlink LLC(ARQ) module 1252 can also perform fragmentation of higher layermessages, e.g., packets, into multiple sub-portions, e.g., frames to besent by downlink PHY/MAC module 1254. Configuration information 1230 caninclude configuration information that affects the operation of downlinkLLC (ARQ) module 1252, e.g., an ARQ window size, maximum number ofretransmissions, a discard timer, etc.

Downlink PHY/MAC module 1254 controls PHY layer and MAC layer processingrelating to sending data information, e.g., messages, packets, and/orframes, by way of wireless communication interface module 1208, e.g.,from access node 1200 to an end node. In some embodiments, operation ofdownlink PHY/MAC module 1254 includes both sending and receiving controlinformation, e.g., signals or messages, to coordinate sending of datainformation, e.g., messages, packets, or frames. Configurationinformation 1230 can include configuration information that affects theoperation of downlink PHY/MAC module 1254, e.g., a frequency, band,channel, spreading code or hoping code to be used for transmissions, anidentifier associated with the access node 1200, etc.

FIG. 13 illustrates example signaling and traffic flows between variousmodules included in example end node 1100 and example access node 1200.The FIG. 13 end node 1100 and FIG. 13 access node 1200 are simplifiedrepresentations of the FIG. 11 end node 1100 and FIG. 12 access node1200, respectively. The FIG. 13 example shows application module 1128sending and receiving data information, e.g., traffic flows comprising asequence of messages, packets, or frames. In the context of the FIG. 10example system, the FIG. 13 end node 1100 may be any one of end nodes1002-1012 depicted in FIG. 10 and the application module 1128 includedin the FIG. 13 end node 1100 may be exchanging data information withanother node in the system, e.g., another end node 1002-1012 or theapplication server node 1026 as depicted in FIG. 10. In FIG. 13 and thesubsequent description, the node with which the FIG. 13 end node 1100 isexchanging data information is referred to as the corresponding node.

The data information, e.g., traffic flows comprising a sequence ofmessages, packets, or frames, sent from the application module 1128 inthe end node 1100 to a corresponding node is shown by a sequence ofarrows 1302-1308 to proceed through a sequence of modules 1138-1144included in end node 1100 for processing, after which the datainformation is sent from the end node 1100 to the access node 1200,e.g., by way of wireless communication interface module 1104. Followingreception by access node 1200, e.g., by way of wireless communicationinterface module 1208, the data information, e.g., traffic flowscomprising a sequence of messages, packets, or frames, sent from theapplication module 1128 in end node 1100 to the corresponding node isshown by a sequence of arrows 1310-1318 to proceed through a sequence ofmodules 1238-1244 included in access node 1200 for processing, prior tobeing forwarded from the access node 1200 toward the corresponding node,e.g., directed in accordance with routing information to an intermediatenode connected to the access node by way of network/internetworkinterface module 1206.

The data information, e.g., traffic flows comprising a sequence ofmessages, packets, or frames, sent from a corresponding node toapplication module 1128 in end node 1128 is shown by a sequence ofarrows 1320-1328 to be received by access node 1200, e.g., by way ofnetwork/internetwork interface module 1206, and then to proceed througha sequence of modules 1246-1254 included in access node 1200 forprocessing, after which the data information is sent from the accessnode 1200 to the end node 1100, e.g., via the wireless communicationinterface module 1208. Following reception by end node 1100, e.g., byway of wireless communication interface module 1104, the datainformation, e.g., traffic flows comprising a sequence of messages,packets, or frames, sent from the corresponding node to applicationmodule 1128 in end node 1100 is shown by a sequence of arrows 1330-1334to proceed through a sequence of modules 1146 and 1148 included in endnode 1100 for processing, prior to being delivered to the applicationmodule 1128 in end node 1100.

In addition to the exchange of data information, e.g., traffic flows,FIG. 13 also depicts the exchange of control information, e.g.,signaling flows and/or communication interfaces. In particular, the FIG.13 example depicts the exchange of control information between controlsignaling module 1226 and traffic control module 1228 included in accessnode 1200. Similarly, the FIG. 13 example depicts the exchange ofcontrol information between control signaling module 1126 and thetraffic control module 1130 included in the end node 1100. In bothaccess node 1200 and end node 1100, exchange of control informationbetween the modules as shown allows the respective control signalingmodule 1226/1126 in the access/end node 1200/1100 to affect, e.g., set,modify, and/or monitor, the configuration and/or operation of thevarious modules included in the respective traffic control module1228/1130, as needed to provide the proper quality of service treatmentof the data information, e.g., traffic flows, to/from the applicationmodule 1128 in the end node 1100.

The exchange of control information, e.g., signaling flows and/orcommunication interfaces, is also shown a) between another node andcontrol signaling module 1226 in access node 1200, b) betweenapplication module 1128 in end node 1100 and control signaling module1126 in end node 1100, and c) between the respective control signalingmodules 1226/1126 in access node 1200 and end node 1100. These exchangesof control information, e.g., signaling flows and/or communicationinterfaces, enable the configuration and/or operation of traffic controlmodules 1228/1130 in both access node 1200 and the end node 1100 to beaffected by a) one or more additional nodes, e.g. the access controlnode 1020 and/or application server node 1026, b) application module1128 in end node 1100, or c) a combination of one or more additionalnodes and the application module 1128 in end node 1100. Variousembodiments of the present invention may, and do, support all or only asubset of the depicted control information exchanges as needed.

What has been described above includes examples of one or moreembodiments. It is, of course, not possible to describe everyconceivable combination of components or methodologies for purposes ofdescribing the aforementioned embodiments, but one of ordinary skill inthe art may recognize that many further combinations and permutations ofvarious embodiments are possible. Accordingly, the described embodimentsare intended to embrace all such alterations, modifications andvariations that fall within the spirit and scope of the appended claims.Furthermore, to the extent that the term “includes” is used in eitherthe detailed description or the claims, such term is intended to beinclusive in a manner similar to the term “comprising” as “comprising”is interpreted when employed as a transitional word in a claim.

1-31. (canceled)
 32. A method, comprising: receiving a first pluralityof media streams generated at an event; enabling a wireless terminal toreceive the first plurality of media streams broadcast over at least onemedia distribution system (MDS) on a wireless network in which a serviceprovider operates a signal on a dedicated frequency inside the locationof the event that is treated as a separate wireless network from a largearea network, wherein the separate wireless network is substantiallylimited in range to the location of the event and the large area networkprovides a second plurality of media streams; and interfacing to thefirst plurality of media channels in order for the wireless terminal toselect the subset of the plurality of media channels for viewing. 33.The method of claim 32, wherein the first plurality of media streamsinclude video data, audio data, or textual information.
 34. The methodof claim 32, further comprising monitoring radio frequency (RF)allocation tables in the separate wireless network.
 35. The method ofclaim 32, further comprising selecting the subset of the first pluralityof media streams from a program guide.
 36. The method of claim 32,further comprising generating multiple camera views at the wirelessterminal.
 37. An apparatus, comprising: a memory that retainsinstructions configured to cause a processor to perform operationscomprising: receiving a first plurality of media streams generated at anevent; enabling a wireless terminal to receive the first plurality ofmedia streams broadcast over at least one media distribution system(MDS) on a wireless network in which a service provider operates asignal on a dedicated frequency inside the location of the event that istreated as a separate wireless network from a large area network,wherein the separate wireless network is substantially limited in rangeto the location of the event and the large area network provides asecond plurality of media streams, and interfacing to the firstplurality of media streams in order for the wireless terminal to selecta subset of the first plurality of media streams for desired viewing;and a processor that executes the instructions to perform theoperations.
 38. The apparatus of claim 37, further comprising acomponent to enable a device to receive the first plurality of mediastreams.
 39. A communications apparatus, comprising: means for receivinga first plurality of media streams generated at an event; means forenabling a wireless terminal to receive the first plurality of mediastreams broadcast over at least one media distribution system (MDS) on awireless network in which a service provider operates a signal on adedicated frequency inside the location of the event that is treated asa separate wireless network from a large area network, wherein theseparate wireless network is substantially limited in range to thelocation of the event and the large area network provides a secondplurality of media streams; and means for interfacing to the firstplurality of media streams in order for the wireless terminal to selecta subset of the first media streams for desired viewing.
 40. Anon-transitory computer readable storage medium having stored thereoncomputer-executable instructions configured to cause a computer toperform operations comprising: receiving a first plurality of mediastreams generated at an event; enabling a wireless terminal to receivethe first plurality of media streams broadcast over at least one mediadistribution system (MDS) on a wireless network in which a serviceprovider operates a signal on a dedicated frequency inside the locationof the event that is treated as a separate wireless network from a largearea network, wherein the separate wireless network is substantiallylimited in range to the location of the event and the large area networkprovides a second plurality of media streams; and interfacing to thefirst plurality of media streams in order for the wireless terminal toselect a subset of the first plurality of media streams for desiredviewing.
 41. (canceled)
 42. The apparatus of claim 37, wherein the firstplurality of media streams include video data, audio data, or textualinformation.
 43. The apparatus of claim 37, wherein the memory retainsinstructions configured to perform operations further comprisingmonitoring radio frequency (RF) allocation tables in the separatewireless network.
 44. The apparatus of claim 37, wherein the memoryretains instructions configured to cause a processor to performoperations further comprising selecting the first plurality of mediastreams from a program guide.
 45. The communications apparatus of claim39, wherein the first plurality of media streams include video data,audio data, or textual information.
 46. The communications apparatus ofclaim 39, further comprising means for monitoring radio frequency (RF)allocation tables in the separate wireless network.
 47. Thecommunications apparatus of claim 39, further comprising means forselecting the first plurality of media streams from a program guide. 48.The non-transitory computer readable storage medium of claim 40, whereinthe first plurality of media streams include video data, audio data, ortextual information.
 49. The non-transitory computer readable storagemedium of claim 40, wherein the stored computer-executable instructionsare configured to cause the computer to perform operations furthercomprising monitoring radio frequency (RF) allocation tables in theseparate wireless network.
 50. The non-transitory computer readablestorage medium of claim 49, wherein the stored computer-executableinstructions are configured to cause the computer to perform operationsfurther comprising selecting the first plurality of media streams from aprogram guide.